Remove outdated content provider list and update peering documentation #2119
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 Build Preview on IPFS ready
|
2color
force-pushed
the
remove-peering
branch
2 times, most recently
from
c0f1cf6 to
a3bd938
Compare
lidel
approved these changes
Aug 25, 2025
|
There is far too much tribal knowledge present in the IPFS ecosystem. Removing this list is a step in the wrong direction. |
Can you please explain the reasoning? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
The content provider list contained many peers that are no longer online. Rather than maintaining a list that's bound to get outdated and mislead users, this PR removes the provider list entirely and focuses the documentation on the core peering concepts and configuration.
More broadly, reprovide sweep should bring significant improvements to the DHT, which should eliminate many of the content routing problems experienced by the community.